…s variants

The stored form mirrors `ContestedIndexResolution` variant for variant under
the same names. With the vote among documents it has three, all starting
`MasternodeVote`, which clippy's `enum_variant_names` refuses on a non-public
enum.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

Review of the contest among documents:

- The index parser took the decision to read `"resolution": 2` as a flag on
  its admissions, set by its callers from `parse_contested_documents_resolution`
  with `is_some()`. It is now a versioned method,
  `ContestedIndexResolution::try_from_schema_value`, taking the platform
  version: `None` converts the value as it always was, version 0 also reads 2,
  and any other version is refused with `UnknownVersionMismatch`. The schema
  parser and the registration cost both parse an index through
  `Index::try_from_value_map_for_platform_version`, which calls it;
  `Index::try_from_value_map` keeps the conversion that predates it. The
  admissions struct is as it was.
- The comments of the decision proposals crate no longer say an identity
  enters one choice.
- The contender, vote choice, winner and proof result docs say that the id
  naming a contender is its document's id in a vote among documents.
- A test proves and verifies the vote state of a proposal whose choices
  include two from one identity, while the vote runs and after it ends.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…(PV15)

A `permanentDocument` or `moderatedDocument` `refersTo` on an identifier
property may leave its target to the referring document: `contractIdProperty`
and `documentTypeProperty` name the properties holding the contract and the
document type, in place of `contractId` and `documentType`, and
`documentTypeRequirements` says what the named type must look like: named
slots, each a property it must have (`name`: `"$any"`, a property name, or a
name read from the referring document; `type`; `maxBytes`; `distinctFrom`),
and `require`, `anyOf` / `allOf` over slot names.

Version 1 of `apply_property_reference` (protocol version 15) parses the
declaration to `DocumentPropertyReferenceTarget::DynamicDocument`, appended,
and refuses its keys wherever else a reference sits. Nothing about the
target is known at registration, so `document_reference_validation` 1 checks
it when a document is written: the contract and the type exist, the type is
not private, meets the requirements
(`ReferencedDocumentTypeRequirementNotMetError`, 40153) and is of the
declared kind, and the document exists. A replace checks the reference
again when its value or a property it reads the target from changed.

Protocol version 14 and earlier keep `apply_property_reference` 0, which
does not read the keys.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…stration fee

The registration cost of a state transition is read from the schema, where an
index that does not parse is charged nothing. A vote among documents
(`resolution` 2) parses there through the versioned index parse; this holds the
fee to it, from the contract and from the serialization format, beside the two
resolutions that predate it.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…-named references (PV15)

A refersTo naming its target through the referring document may list both
kinds, ["permanentDocument", "moderatedDocument"]: the named type is then
either, and the reference is checked as one of the kind the type is.

A documentTypeRequirements slot may carry `when`, a condition in the forms
of a propertyConstraints condition read against the referenced type:
$kind, $self, $moderatorAbilities.deleteKeepsFields,
$moderatorAbilities.changeFields and { "const": ... }. A property the
condition does not hold for does not fill the slot. So a contract can ask
that a text it points at is one a moderator's removal takes away, only
when the type is a moderated one.

The condition is stored in the compiled contract and carried by consensus
errors, so its decoders refuse a nesting past 16, and the parser holds one
`when` to max_document_type_requirement_condition_nodes (16).

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…ecision-proposal-description-reference

Brings the multiple choice proposal types together with the references
whose target the document names. The two protocol version 15 notes
numbered 33 become 33 (a contest among documents) and 34 (a reference
whose target the document names).

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…m a moderated text (PV15)

A multipleChoiceProposal no longer holds a description. It points at a
document saying what is being decided (descriptionId), of the contract and
the document type it names (descriptionContractId,
descriptionDocumentType):

- the document type is a moderated one holding a string or a byte array
  that a moderator's removal takes away and that its author writes;
- the contract declares moderators the masternodes elect.

So a description can be taken down while the proposal, which is
undeletable, and its vote stay. The three properties may change for two
hours after the proposal is created, like its title and url.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…-when

Brings in the review fixes of the base: the indexOnly refusal (40146), the
reference inputs a moderator may not write, the rule message, and the
schema shape of documentTypeRequirements written by rs-dpp.

A slot's `when` follows that shape into rs-dpp
(SlotCondition::to_schema_value, which the parser reads back), so
wasm-dpp2 no longer builds it itself.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…posal-description-reference

Brings in the review fixes of the references whose target the document
names: the indexOnly refusal (40146), the reference inputs a moderator may
not write, and the schema shape of documentTypeRequirements written by
rs-dpp.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

The message refusing a refersTo that names its target through the
referring document on a property that is not an identifier held a run of
spaces where its two lines join. It travels in a consensus error, so it is
fixed before protocol version 15 ships, and its test now holds the whole
sentence.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…laude/dynamic-refers-to-when

Brings in the restored line continuation of a dynamic reference refusal.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…posal-description-reference

Brings in the restored line continuation of a dynamic reference refusal.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…laude/dynamic-refers-to-when

Brings in the second review's fixes of the base: `require` names nothing
twice, the book's client assignment rule chooses the set of slots first,
and a test of the assignment search taking a property back.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…posal-description-reference

Brings in the second review's fixes of the references whose target the
document names: `require` names nothing twice, and the book's client
assignment rule chooses the set of slots first.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…Id and documentType

A refersTo whose target the referring document names no longer has keys of
its own for it. It writes the keys every document reference has, read from
the document:

    "contractId": "$self.descriptionContractId",
    "documentType": "$self.descriptionDocumentType"

in place of contractIdProperty and documentTypeProperty. `$self` is the
document being written, as `$old` is the stored one in a rule. A slot's
name read from the document follows: "$self.bodyProperty" in place of
{ "property": "bodyProperty" }.

Both are read from the document or neither: one of them literal, or left
out, beside the other is refused, as is documentTypeRequirements beside a
target the schema names. Protocol version 14 gives the prefix no meaning
and refuses such a declaration. What is stored is unchanged.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…posal-description-reference

Brings in the target read through `$self.` and the `when` operand renamed
`$property`, and writes the multiple choice proposal's description with
them:

    "contractId": "$self.descriptionContractId",
    "documentType": "$self.descriptionDocumentType",
    ... { "not": { "contains": ["$moderatorAbilities.deleteKeepsFields", "$property"] } }

What the reference means is unchanged. The schema's bytes are not, so the
ten genesis root pins of nullifier_batch_guard move with it.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

A string property declaring both maxLength and maxBytes was held to its
maxBytes alone when a slot's maxBytes was checked, so one of at most two
characters (eight bytes) with a maxBytes of 100 failed a slot of eight
bytes it can never exceed. The bound is now the smaller of maxBytes and
four bytes a character of maxLength.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…laude/dynamic-refers-to-when

Brings in the tighter of a string property's two bounds when a slot's
maxBytes is checked.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…posal-description-reference

Brings in the tighter of a string property's two bounds when a slot's
maxBytes is checked.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…ecision-proposal-description-reference

Brings in v5.1-dev at 78d691d, which now holds the either-kind targets and
slot `when` change (#5850) as a squash, together with the multiple choice
proposals branch this one is built on.

- Files #5850's squash left identical to its last head keep this branch's
  version, which adds the type-level `when`, `$electedAbilities` and the
  `present`/`absent` conditions on top of it.
- document_reference_validation 1 keeps reading the elected team's abilities
  for the named type before judging its requirements.
- Protocol version 15 notes read 33 (reference whose target the document
  names, with the type-level `when`), 34 (keys with a budget), 35 (composite
  document history), 36 (a contest among documents).
- The ten nullifier_batch_guard roots and the activation root are recomputed
  for this branch's decision proposals schema on the new base.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…ecision-proposal-description-reference

- A choice may be neither changed nor deleted by anyone, yet the end of its
  vote removes the choices that were not kept: the README said "never deleted".
- The fund a choice pays doubles once the vote holds 250 choices and again for
  every 50 more, as the protocol guide already says; the README gave 0.1 Dash
  alone.
- The protocol guide says where the ids of the choices not kept are read: the
  stored result, which the vote state query returns, lists every choice by its
  document id with its tally.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…ecision-proposal-description-reference

Brings in v5.1-dev at 8b4ca80 (the pin of the bytes protocol version 15
stores contracts in, #5880, and the array depth fix of validate_max_depth 2,
#5881) and the multiple choice proposals branch's README and protocol guide
wording on when a choice leaves state and how its fund grows.

The stored contract fixture is regenerated for the one contract this branch
changes: the decision proposals contract, whose `multipleChoiceProposal`
names its description through a reference here. No other line of
`stored.jsonl` changes.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…ecision-proposal-description-reference

Brings in v5.1-dev at 1f36c10: an insert writes no entry in an expired
time range bucket (#5877), which took protocol version 15 note 36, so the
multiple choice proposals branch's "A contest among documents" is 37. The
merge is clean and no root pin, fee pin or stored contract fixture line
changes.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…ecision-proposal-description-reference

Brings in v5.1-dev at 97fb5f9: a refersTo is read as dynamic only where
protocol version 14 cannot read it (#5887).

The one conflict is protocol version 15 note 33, where both sides added a
sentence: it keeps this branch's use of the reference by the decision
proposals contract and the base's statement of which declarations version 1
reads as dynamic. The parser and its tests merge cleanly: the description
reference is a `moderatedDocument` whose `contractId` is written `$self.`,
which stays dynamic. No root pin, fee pin or stored contract fixture line
changes.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

A tie goes to the earliest choice by creation time, then block height, then
core block height, and choices entered in the same block share all three:
among them the lower document id wins, not the one entered first. The
protocol guide and the README said only "the earliest choice", and the guide
that a vote nobody votes in keeps the first choice entered.

Co-Authored-By: Claude Fable 5.2 <[email protected]>

…ecision-proposal-description-reference